WireMod Closure Update for icaruscode develop - #913
Conversation
…e CMakeLists.txt file
…PropertiesData. Also change some MessageFacility calls
…age of SignalROIF, rounding of floats, fixed scaling factors to 1 at al. )
Moved the TGraph2D interpolation to an option (UseGraph2DInterpolation), default is true. Renamed the fcls with _pops_ to _develop_ (bad practice on my local branch that got picked up) Added a fcl for null-wiremod modification. Added a fcl for the full diagnostic available in ntuples, including the modified ROIs.
…n channelROI to recob::Wire. There is a different approach which should be used in the future and can be tested with UseChannelROIMode: true, which Harry introduced to skip these conversions. UseChannelROIMode is ideal, but it was tested with a small sample, need higher stats check to verify that closure is achieved also in this way.
There was a problem hiding this comment.
is this the best place for the ratio to live? it's probably fine, but a dedicated storage directory might be a good idea
hausnerh
left a comment
There was a problem hiding this comment.
I think this looks good. There are some older modules included in here that I wrote way back when initially testing, and idk if they are strictly necessary and we might want to pare down this merge to simplify what goes into develop, but it's not breaking and probably nobody but me would even look at those files anyways
|
trigger build LArSoft/lar*@LARSOFT_SUITE_v10_22_00 SBNSoftware/sbn*@SBN_SUITE_v10_22_00 |
|
✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard |
|
❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for c14:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build ICARUS phase logs parent CI build details are available through the CI dashboard |
|
✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard |
|
❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for e26:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build ICARUS phase logs parent CI build details are available through the CI dashboard |
|
trigger build LArSoft/lar*@LARSOFT_SUITE_v10_22_00 SBNSoftware/sbn*@SBN_SUITE_v10_22_00 SBNSoftware/sbndaq-artdaq-core@v1_10_06 |
|
✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard |
|
✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard |
|
❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for c14:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build ICARUS phase logs parent CI build details are available through the CI dashboard |
|
❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for e26:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build ICARUS phase logs parent CI build details are available through the CI dashboard |
|
trigger build LArSoft/lar*@LARSOFT_SUITE_v10_22_00 SBNSoftware/sbndaq-artdaq-core@v1_10_06 SBNSoftware/sbn*@SBN_SUITE_v10_22_00 |
|
✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard |
|
❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for c14:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build ICARUS phase logs parent CI build details are available through the CI dashboard |
|
✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard |
|
❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for e26:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build ICARUS phase logs parent CI build details are available through the CI dashboard |
|
@francescopoppi, @gputnam, and @hausnerh, Looks like there are some badly named/linked modules (see end of this comment) that need fixing before this PR can build. The twin PR (#918) for production did not have such errors (or the authors remedied things before I started the release manager's build). Might be good to model things after that PR if it still makes sense with how production has diverged from develop. It's also possible that something was incorrectly propagated from production to develop in the recent migration. Let me know if I should pull over some changes to get things to build if addressing the errors below goes directly against your intention/intuition. |
No description provided.